Mobile device session analyzer

ABSTRACT

Techniques described herein relate to determining performance conditions for mobile device execution sessions based on analyses of session context data and performance data associated with content resource execution sessions. Mobile devices may receive and execute content resources via input/output subsystems, during which feedback data by the mobile devices. Mobile devices also may be configured to detect and/or determine context data associated with specific content resource execution sessions, using device sensors and other techniques. Session analyzers may receive and analyze content resource execution session data received from one or more mobile devices, and determine user performance conditions for content resource execution sessions.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation of U.S. Non-Provisional applicationSer. No. 14/850,595, entitled “MOBILE DEVICE SESSION ANALYZER”, filed onSep. 10, 2015, which is incorporated herein by reference in its entiretyfor all purposes.

BACKGROUND

Effective performance and interactions during execution sessions onmobile devices is often challenging. Different mobile devices may haveunique sets of device capabilities and characteristics. Additionally,multiple mobile devices may be related and used to perform similar tasksand execute related sets of content resources. Certain mobile device maybe personal and individual devices, while others may be shared devices.Moreover, the computing conditions and physical environments in whichmobile devices are used to perform tasks and execute resources may beconstantly changing. For example, mobile devices may be used atdifferent times and places, and in different network conditions,physical environments, and the like, which may result in varying andunpredictable performance during different content resource executionsessions.

BRIEF SUMMARY

Various techniques (e.g., systems, methods, computer-program productstangibly embodied in a non-transitory machine-readable storage medium,etc.) are described herein for determining performance conditions formobile device execution sessions based on analyses of session contextdata and performance data associated with content resource executionsessions. Mobile devices may receive and execute content resources viainput/output subsystems, during which feedback data by the mobiledevices. Mobile devices also may be configured to detect and/ordetermine context data associated with specific content resourceexecution sessions, using device sensors and other techniques. Sessionanalyzers may receive and analyze content resource execution sessiondata received from one or more mobile devices, and determine userperformance conditions for content resource execution sessions.

Additional techniques discussed herein relate to monitoring one or moremobile devices after set of performance conditions have been determinedfor the mobile devices and/or associated users. Current context data foreach mobile device may be tracked and monitored, in order to providenotifications and resource suggestions based on performance conditionsassociated with users, mobile devices, and/or content resource types.Further techniques described herein relate to determining performanceconditions and monitoring mobile device context data based on groups ofrelated content resource execution sessions.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing illustrating an example of a contentdistribution network.

FIG. 2 is a block diagram illustrating a computer server and computingenvironment within a content distribution network.

FIG. 3 is a block diagram illustrating an embodiment of one or more datastore servers within a content distribution network.

FIG. 4 is a block diagram illustrating an embodiment of one or morecontent management servers within a content distribution network.

FIG. 5 is a block diagram illustrating the physical and logicalcomponents of a special-purpose computer device within a contentdistribution network.

FIG. 6 is a block diagram illustrating an example system including amobile device session analyzer and a plurality of mobile devices,according to one or more embodiments of the disclosure.

FIGS. 7A and 7B are illustrative data tables containing example sets ofmobile device data and session data, according to one or moreembodiments of the disclosure.

FIG. 8 is a block diagram illustrating another example system includinga mobile device session analyzer and a plurality of mobile devices,according to one or more embodiments of the disclosure.

FIG. 9 is a flow diagram illustrating an example process of determiningperformance conditions corresponding to a user's content resourceexecution sessions, according to one or more embodiments of thedisclosure.

FIGS. 10A and 10B are illustrative data tables containing exampleperformance condition data, according to one or more embodiments of thedisclosure.

FIG. 11 is a flow diagram illustrating an example process of determininga set of content resources based on the current context data of a mobiledevice, according to one or more embodiments of the disclosure.

FIG. 12 is a flow diagram illustrating an example process of determiningcontent resources to present to a user based on the current context dataof a mobile device, according to one or more embodiments of thedisclosure.

FIG. 13 is an illustrative user interface of a mobile device providing anotification to a user in response to evaluating the performanceconditions for the user based on the current context data of the mobiledevice, according to one or more embodiments of the disclosure.

FIG. 14 is an illustrative user interface of a mobile device providing aset of content suggestions to a user based on the current context dataof the mobile device, according to one or more embodiments of thedisclosure.

FIG. 15 is a flow diagram illustrating an example process of determiningperformance conditions corresponding to a user's group of contentresource execution sessions, according to one or more embodiments of thedisclosure.

FIG. 16 is an illustrative data table containing example session groupdata, according to one or more embodiments of the disclosure.

FIG. 17 is an illustrative user interface of a mobile device providing anotification to a user in response to evaluating the session groupperformance conditions for the user, according to one or moreembodiments of the disclosure.

In the appended figures, similar components and/or features may have thesame reference label. Further, various compo of the same type may bedistinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If only the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

DETAILED DESCRIPTION

The ensuing description provides illustrative embodiment(s) only and isnot intended to limit the scope, applicability or configuration of thedisclosure. Rather, the ensuing description of the illustrativeembodiment(s) will provide those skilled in the art with an enablingdescription for implementing a preferred exemplary embodiment. It isunderstood that various changes can be made in the function andarrangement of elements without departing from the spirit and scope asset forth in the appended claims.

With reference now to FIG. 1, a block diagram is shown illustratingvarious components of a content distribution network (CDN) 100 whichimplements and supports certain embodiments and features describedherein. Content distribution network 100 may include one or more contentmanagement servers 102. As discussed below in more detail, contentmanagement servers 102 may be any desired type of server including, forexample, a rack server, a tower server, a miniature server, a bladeserver, a mini rack server, a mobile server, an ultra-dense server, asuper server, or the like, and may include various hardware components,for example, a motherboard, a processing units, memory systems, harddrives, network interfaces, power supplies, etc. Content managementserver 102 may include one or more server farms, clusters, or any otherappropriate arrangement and/or combination or computer servers. Contentmanagement server 102 may act according to stored instructions locatedin a memory subsystem of the server 102, and may run an operatingsystem, including any commercially available server operating systemand/or any other operating systems discussed herein.

The content distribution network 100 may include one or more data storeservers 104, such as database servers and file-based storage systems.Data stores 104 may comprise stored data relevant to the functions ofthe content distribution network 100. Illustrative examples of datastores 104 that may be maintained in certain embodiments of the contentdistribution network 100 are described below in reference to FIG. 3. Insome embodiments, multiple data stores may reside on a single server104, either using the same storage components of server 104 or usingdifferent physical storage components to assure data security andintegrity between data stores. In other embodiments, each data store mayhave a separate dedicated data store server 104.

Content distribution network 100 also may include one or more userdevices 106 and/or supervisor devices 110. User devices 106 andsupervisor devices 110 may display content received via the contentdistribution network 100, and may support various types of userinteractions with the content. User devices 106 and supervisor devices110 may include mobile devices such as smartphones, tablet computers,personal digital assistants, and wearable computing devices. Such mobiledevices may run a variety of mobile operating systems, and may beenabled for Internet, e-mail, short message service (SMS), Bluetooth®,mobile radio-frequency identification (M-RFID), and/or othercommunication protocols. Other user devices 106 and supervisor devices110 may be general purpose personal computers or special-purposecomputing devices including, by way of example, personal computers,laptop computers, workstation computers, projection devices, andinteractive room display systems. Additionally, user devices 106 andsupervisor devices 110 may be any other electronic devices, such asthin-client computers, Internet-enabled gaming systems, business or homeappliances, and/or personal messaging devices, capable of communicatingover network(s) 120.

In different contexts of content distribution networks 100, user devices106 and supervisor devices 110 may correspond to different types ofspecialized devices, for example, student devices and teacher devices inan educational network, employee devices and presentation devices in acompany network, different gaming devices in a gaming network, etc. Insome embodiments, user devices 106 and supervisor devices 110 mayoperate in the same physical location 107, such as a classroom orconference room. In such cases, the devices may contain components thatsupport direct communications with other nearby devices, such as awireless transceivers and wireless communications interfaces, Ethernetsockets or other Local Area Network (LAN) interfaces, etc. In otherimplementations, the user devices 106 and supervisor devices 110 neednot be used at the same location 107, but may be used in remotegeographic locations in which each user device 106 and supervisor device110 may use security features and/or specialized hardware (e.g.,hardware-accelerated SSL and HTTPS, WS-Security, firewalls, etc.) tocommunicate with the content management server 102 and/or other remotelylocated user devices 106. Additionally, different user devices 106 andsupervisor devices 110 may be assigned different designated roles, suchas presenter devices, teacher devices, administrator devices, or thelike, and in such cases the different devices may be provided withadditional hardware and/or software components to provide content andsupport user capabilities not available to the other devices.

The content distribution network 100 also may include a privacy server108 that maintains private user information at the privacy server 108while using applications or services hosted on other servers. Forexample, the privacy server 108 may be used to maintain private data ofa user within one jurisdiction even though the user is accessing anapplication hosted on a server (e.g., the content management server 102)located outside the jurisdiction. In such cases, the privacy server 108may intercept communications between a user device 106 or supervisordevice 110 and other devices that include private user information. Theprivacy server 108 may create a token or identifier that does notdisclose the private information and may use the token or identifierwhen communicating with the other servers and systems, instead of usingthe user's private information.

As illustrated in FIG. 1, the content management server 102 may be incommunication with one or more additional servers, such as a contentserver 112, a user data server 112, and/or an administrator server 116.Each of these servers may include some or all of the same physical andlogical components as the content management server(s) 102, and in somecases, the hardware and software components of these servers 112-116 maybe incorporated into the content management server(s) 102, rather thanbeing implemented as separate computer servers.

Content server 112 may include hardware and software components togenerate, store, and maintain the content resources for distribution touser devices 106 and other devices in the network 100. For example, incontent distribution networks 100 used for professional training andeducational purposes, content server 112 may include data stores oftraining materials, presentations, interactive programs and simulations,course models, course outlines, and various training interfaces thatcorrespond to different materials and/or different types of user devices106. In content distribution networks 100 used for media distribution,interactive gaming, and the like, a content server 112 may include mediacontent files such as music, movies, television programming, games, andadvertisements.

User data server 114 may include hardware and software components thatstore and process data for multiple users relating to each user'sactivities and usage of the content distribution network 100. Forexample, the content management server 102 may record and track eachuser's system usage, including their user device 106, content resourcesaccessed, and interactions with other user devices 106. This data may bestored and processed by the user data server 114, to support usertracking and analysis features. For instance, in the professionaltraining and educational contexts, the user data server 114 may storeand analyze each user's training materials viewed, presentationsattended, courses completed, interactions, evaluation results, and thelike. The user data server 114 may also include a repository foruser-generated material, such as evaluations and tests completed byusers, and documents and assignments prepared by users. In the contextof media distribution and interactive gaming, the user data server 114may store and process resource access data for multiple users (e.g.,content titles accessed, access times, data usage amounts, gaminghistories, user devices and device types, etc.).

Administrator server 116 may include hardware and software components toinitiate various administrative functions at the content managementserver 102 and other components within the content distribution network100. For example, the administrator server 116 may monitor device statusand performance for the various servers, data stores, and/or userdevices 106 in the content distribution network 100. When necessary, theadministrator server 116 may add or remove devices from the network 100,and perform device maintenance such as providing software updates to thedevices in the network 100. Various administrative tools on theadministrator server 116 may allow authorized users to set user accesspermissions to various content resources, monitor resource usage byusers and devices 106, and perform analyses and generate reports onspecific network users and/or devices (e.g., resource usage trackingreports, training evaluations, etc.).

The content distribution network 100 may include one or morecommunication networks 120. Although only a single network 120 isidentified in FIG. 1, the content distribution network 100 may includeany number of different communication networks between any of thecomputer servers and devices shown in FIG. 1 and/or other devicesdescribed herein. Communication networks 120 may enable communicationbetween the various computing devices, servers, and other components ofthe content distribution network 100. As discussed below, variousimplementations of content distribution networks 100 may employdifferent types of networks 120, for example, computer networks,telecommunications networks, wireless networks, and/or any combinationof these and/or other networks.

With reference to FIG. 2, an illustrative distributed computingenvironment 200 is shown including a computer server 202, four clientcomputing devices 206, and other components that may implement certainembodiments and features described herein. In some embodiments, theserver 202 may correspond to the content management server 102 discussedabove in FIG. 1, and the client computing devices 206 may correspond tothe user devices 106. However, the computing environment 200 illustratedin FIG. 2 may correspond to any other combination of devices and serversconfigured to implement a client-server model or other distributedcomputing architecture.

Client devices 206 may be configured to receive and execute clientapplications over one or more networks 220. Such client applications maybe web browser based applications and/or standalone softwareapplications, such as mobile device applications. Server 202 may becommunicatively coupled with the client devices 206 via one or morecommunication networks 220. Client devices 206 may receive clientapplications from server 202 or from other application providers (e.g.,public or private application stores). Server 202 may be configured torun one or more server software applications or services, for example,web-based or cloud-based services, to support content distribution andinteraction with client devices 206. Users operating client devices 206may in turn utilize one or more client applications (e.g., virtualclient applications) to interact with server 202 to utilize the servicesprovided by these components.

Various different subsystems and/or components 204 may be implemented onserver 202. Users operating the client devices 206 may initiate one ormore client applications to use services provided by these subsystemsand components. The subsystems and components within the server 202 andclient devices 206 may be implemented in hardware, firmware, software,or combinations thereof. Various different system configurations arepossible in different distributed computing systems 200 and contentdistribution networks 100. The embodiment shown in FIG. 2 is thus oneexample of a distributed computing system and is not intended to belimiting.

Although exemplary computing environment 200 is shown with four clientcomputing devices 206, any number of client computing devices may besupported. Other devices, such as specialized sensor devices, etc., mayinteract with client devices 206 and/or server 202.

As shown in FIG. 2, various security and integration components 208 maybe used to send and manage communications between the server 202 anduser devices 206 over one or more communication networks 220. Thesecurity and integration components 208 may include separate servers,such as web servers and/or authentication servers, and/or specializednetworking components, such as firewalls, routers, gateways, loadbalancers, and the like. In some cases, the security and integrationcomponents 208 may correspond to a set of dedicated hardware and/orsoftware operating at the same physical location and under the controlof same entities as server 202. For example, components 208 may includeone or more dedicated web servers and network hardware in a datacenteror a cloud infrastructure. In other examples, the security andintegration components 208 may correspond to separate hardware andsoftware components which may be operated at a separate physicallocation and/or by a separate entity.

Security and integration components 208 may implement various securityfeatures for data transmission and storage, such as authenticating usersand restricting access to unknown or unauthorized users. In variousimplementations, security and integration components 208 may provide,for example, a file-based integration scheme or a service-basedintegration scheme for transmitting data between the various devices inthe content distribution network 100. Security and integrationcomponents 208 also may use secure data transmission protocols and/orencryption for data transfers, for example, File Transfer Protocol(FTP), Secure File Transfer Protocol (SFTP), and/or Pretty Good Privacy(PGP) encryption.

In some embodiments, one or more web services may be implemented withinthe security and integration components 208 and/or elsewhere within thecontent distribution network 100. Such web services, includingcross-domain and/or cross-platform web services, may be developed forenterprise use in accordance with various web service standards, such asRESTful web services (i.e., services based on the Representation StateTransfer (REST) architectural style and constraints), and/or webservices designed in accordance with the Web Service Interoperability(WS-I) guidelines. Some web services may use the Secure Sockets Layer(SSL) or Transport Layer Security (TLS) protocol to provide secureconnections between the server 202 and user devices 206. SSL or TLS mayuse HTTP or HTTPS to provide authentication and confidentiality. Inother examples, web services may be implemented using REST over HTTPSwith the OAuth open standard for authentication, or using theWS-Security standard which provides for secure SOAP messages using XMLencryption. In other examples, the security and integration components208 may include specialized hardware for providing secure web services.For example, security and integration components 208 may include securenetwork appliances having built-in features such as hardware-acceleratedSSL and HTTPS, WS-Security, and firewalls. Such specialized hardware maybe installed and configured in front of any web servers, so that anyexternal devices may communicate directly with the specialized hardware.

Communication network(s) 220 may be any type of network familiar tothose skilled in the art that can support data communications using anyof a variety of commercially-available protocols, including withoutlimitation, TCP/IP (transmission control protocol/Internet protocol),SNA (systems network architecture), IPX (Internet packet exchange),Secure Sockets Layer (SSL) or Transport Layer Security (TLS) protocols,Hyper Text Transfer Protocol (HTTP) and Secure Hyper Text TransferProtocol (HTTPS), Bluetooth®, Near Field Communication (NFC), and thelike. Merely by way of example, network(s) 220 may be local areanetworks (LAN), such as one based on Ethernet, Token-Ring and/or thelike. Network(s) 220 also may be wide-area networks, such as theInternet. Networks 220 may include telecommunication networks such as apublic switched telephone networks (PSTNs), or virtual networks such asan intranet or an extranet. Infrared and wireless networks (e.g., usingthe Institute of Electrical and Electronics (IEEE) 802.11 protocol suiteor other wireless protocols) also may be included in networks 220.

Computing environment 200 also may include one or more data stores 210and/or back-end servers 212. In certain examples, the data stores 210may correspond to data store server(s) 104 discussed above in FIG. 1,and back-end servers 212 may correspond to the various back-end servers112-116. Data stores 210 and servers 212 may reside in the samedatacenter or may operate at a remote location from server 202. In somecases, one or more data stores 210 may reside on a non-transitorystorage medium within the server 202. Other data stores 210 and back-endservers 212 may be remote from server 202 and configured to communicatewith server 202 via one or more networks 220. In certain embodiments,data stores 210 and back-end servers 212 may reside in a storage-areanetwork (SAN), or may use storage-as-a-service (STaaS) architecturalmodel.

With reference to FIG. 3, an illustrative set of data stores and/or datastore servers is shown, corresponding to the data store servers 104 ofthe content distribution network 100 discussed above in FIG. 1. One ormore individual data stores 301-309 may reside in storage on a singlecomputer server 104 (or a single server farm or cluster) under thecontrol of a single entity, or may reside on separate servers operatedby different entities and/or at remote locations. In some embodiments,data stores 301-309 may be accessed by the content management server 102and/or other devices and servers within the network 100 (e.g., userdevices 106, supervisor devices 110, administrator servers 116, etc.).Access to one or more of the data stores 301-309 may be limited ordenied based on the processes, user credentials, and/or devicesattempting to interact with the data store.

The paragraphs below describe examples of specific data stores that maybe implemented within some embodiments of a content distribution network100. It should be understood that the below descriptions of data stores301-309, including their functionality and types of data stored therein,are illustrative and non-limiting. Data stores server architecture,design, and the execution of specific data stores 301-309 may depend onthe context, size, and functional requirements of a content distributionnetwork 100. For example, in content distribution systems 100 used forprofessional training and educational purposes, separate databases orfile-based storage systems may be implemented in data store server(s)104 to store trainee and/or student data, trainer and/or professor data,training module data and content descriptions, training results,evaluation data, and the like. In contrast, in content distributionsystems 100 used for media distribution from content providers tosubscribers, separate data stores may be implemented in data storesserver(s) 104 to store listings of available content titles anddescriptions, content title usage statistics, subscriber profiles,account data, payment data, network usage statistics, etc.

A user profile data store 301 may include information relating to theend users within the content distribution network 100. This informationmay include user characteristics such as the user names, accesscredentials (e.g., logins and passwords), user preferences, andinformation relating to any previous user interactions within thecontent distribution network 100 (e.g., requested content, postedcontent, content modules completed, training scores or evaluations,other associated users, etc.).

An accounts data store 302 may generate and store account data fordifferent users in various roles within the content distribution network100. For example, accounts may be created in an accounts data store 302for individual end users, supervisors, administrator users, and entitiessuch as companies or educational institutions. Account data may includeaccount types, current account status, account characteristics, and anyparameters, limits, restrictions associated with the accounts.

A content library data store 303 may include information describing theindividual content items (or content resources) available via thecontent distribution network 100. In some embodiments, the library datastore 303 may include metadata, properties, and other characteristicsassociated with the content resources stored in the content server 112.Such data may identify one or more aspects or content attributes of theassociated content resources, for example, subject matter, access level,or skill level of the content resources, license attributes of thecontent resources (e.g., any limitations and/or restrictions on thelicensable use and/or distribution of the content resource), priceattributes of the content resources (e.g., a price and/or pricestructure for determining a payment amount for use or distribution ofthe content resource), rating attributes for the content resources(e.g., data indicating the evaluation or effectiveness of the contentresource), and the like. In some embodiments, the library data store 303may be configured to allow updating of content metadata or properties,and to allow the addition and/or removal of information relating to thecontent resources. For example, content relationships may be implementedas graph structures, which may be stored in the library data store 303or in an additional store for use by selection algorithms along with theother metadata.

A pricing data store 304 may include pricing information and/or pricingstructures for determining payment amounts for providing access to thecontent distribution network 100 and/or the individual content resourceswithin the network 100. In some cases, pricing may be determined basedon a user's access to the content distribution network 100, for example,a time-based subscription fee, or pricing based on network usage and. Inother cases, pricing may be tied to specific content resources. Certaincontent resources may have associated pricing information, whereas otherpricing determinations may be based on the resources accessed, theprofiles and/or accounts of the user, and the desired level of access(e.g., duration of access, network speed, etc.). Additionally, thepricing data store 304 may include information relating to compilationpricing for groups of content resources, such as group prices and/orprice structures for groupings of resources.

A license data store 305 may include information relating to licensesand/or licensing of the content resources within the contentdistribution network 100. For example, the license data store 305 mayidentify licenses and licensing terms for individual content resourcesand/or compilations of content resources in the content server 112, therights holders for the content resources, and/or common or large-scaleright holder information such as contact information for rights holdersof content not included in the content server 112.

A content access data store 306 may include access rights and securityinformation for the content distribution network 100 and specificcontent resources. For example, the content access data store 306 mayinclude login information (e.g., user identifiers, logins, passwords,etc.) that can be verified during user login attempts to the network100. The content access data store 306 also may be used to storeassigned user roles and/or user levels of access. For example, a user'saccess level may correspond to the sets of content resources and/or theclient or server applications that the user is permitted to access.Certain users may be permitted or denied access to certain applicationsand resources based on their subscription level, training program,course/grade level, etc. Certain users may have supervisory access overone or more end users, allowing the supervisor to access all or portionsof the end user's content, activities, evaluations, etc. Additionally,certain users may have administrative access over some users and/or someapplications in the content management network 100, allowing such usersto add and remove user accounts, modify user access permissions, performmaintenance updates on software and servers, etc.

A source data store 307 may include information relating to the sourceof the content resources available via the content distribution network.For example, a source data store 307 may identify the authors andoriginating devices of content resources, previous pieces of data and/orgroups of data originating from the same authors or originating devices,and the like.

An evaluation data store 308 may include information used to direct theevaluation of users and content resources in the content managementnetwork 100. In some embodiments, the evaluation data store 308 maycontain, for example, the analysis criteria and the analysis guidelinesfor evaluating users (e.g., trainees/students, gaming users, mediacontent consumers, etc.) and/or for evaluating the content resources inthe network 100. The evaluation data store 308 also may includeinformation relating to evaluation processing tasks, for example, theidentification of users and user devices 106 that have received certaincontent resources or accessed certain applications, the status ofevaluations or evaluation histories for content resources, users, orapplications, and the like. Evaluation criteria may be stored in theevaluation data store 308 including data and/or instructions in the formof one or several electronic rubrics or scoring guides for use in theevaluation of the content, users, or applications. The evaluation datastore 308 also may include past evaluations and/or evaluation analysesfor users, content, and applications, including relative rankings,characterizations, explanations, and the like.

In addition to the illustrative data stores described above, data storeserver(s) 104 (e.g., database servers, file-based storage servers, etc.)may include one or more external data aggregators 309. External dataaggregators 309 may include third-party data sources accessible to thecontent management network 100, but not maintained by the contentmanagement network 100. External data aggregators 309 may include anyelectronic information source relating to the users, content resources,or applications of the content distribution network 100. For example,external data aggregators 309 may be third-party data stores containingdemographic data, education related data, consumer sales data, healthrelated data, and the like. Illustrative external data aggregators 309may include, for example, social networking web servers, public recordsdata stores, learning management systems, educational institutionservers, business servers, consumer sales data stores, medical recorddata stores, etc. Data retrieved from various external data aggregators309 may be used to verify and update user account information, suggestuser content, and perform user and content evaluations.

With reference now to FIG. 4, a block diagram is shown illustrating anembodiment of one or more content management servers 102 within acontent distribution network 100. As discussed above, content managementserver(s) 102 may include various server hardware and softwarecomponents that manage the content resources within the contentdistribution network 100 and provide interactive and adaptive content tousers on various user devices 106. For example, content managementserver(s) 102 may provide instructions to and receive information fromthe other devices within the content distribution network 100, in orderto manage and transmit content resources, user data, and server orclient applications executing within the network 100.

A content management server 102 may include a content customizationsystem 402. The content customization system 402 may be implementedusing dedicated hardware within the content distribution network 100(e.g., a content customization server 402), or using designated hardwareand software resources within a shared content management server 102. Insome embodiments, the content customization system 402 may adjust theselection and adaptive capabilities of content resources to match theneeds and desires of the users receiving the content. For example, thecontent customization system 402 may query various data stores andservers 104 to retrieve user information, such as user preferences andcharacteristics (e.g., from a user profile data store 301), user accessrestrictions to content recourses (e.g., from a content access datastore 306), previous user results and content evaluations (e.g., from anevaluation data store 308), and the like. Based on the retrievedinformation from data stores 104 and other data sources, the contentcustomization system 402 may modify content resources for individualusers.

A content management server 102 also may include a user managementsystem 404. The user management system 404 may be implemented usingdedicated hardware within the content distribution network 100 (e.g., auser management server 404), or using designated hardware and softwareresources within a shared content management server 102. In someembodiments, the user management system 404 may monitor the progress ofusers through various types of content resources and groups, such asmedia compilations, courses or curriculums in training or educationalcontexts, interactive gaming environments, and the like. For example,the user management system 404 may query one or more databases and/ordata store servers 104 to retrieve user data such as associated contentcompilations or programs, content completion status, user goals,results, and the like.

A content management server 102 also may include an evaluation system406. The evaluation system 406 may be implemented using dedicatedhardware within the content distribution network 100 (e.g., anevaluation server 406), or using designated hardware and softwareresources within a shared content management server 102. The evaluationsystem 406 may be configured to receive and analyze information fromuser devices 106. For example, various ratings of content resourcessubmitted by users may be compiled and analyzed, and then stored in adata store (e.g., a content library data store 303 and/or evaluationdata store 308) associated with the content. In some embodiments, theevaluation server 406 may analyze the information to determine theeffectiveness or appropriateness of content resources with, for example,a subject matter, an age group, a skill level, or the like. In someembodiments, the evaluation system 406 may provide updates to thecontent customization system 402 or the user management system 404, withthe attributes of one or more content resources or groups of resourceswithin the network 100. The evaluation system 406 also may receive andanalyze user evaluation data from user devices 106, supervisor devices110, and administrator servers 116, etc. For instance, evaluation system406 may receive, aggregate, and analyze user evaluation data fordifferent types of users (e.g., end users, supervisors, administrators,etc.) in different contexts (e.g., media consumer ratings, trainee orstudent comprehension levels, teacher effectiveness levels, gamer skilllevels, etc.).

A content management server 102 also may include a content deliverysystem 408. The content delivery system 408 may be implemented usingdedicated hardware within the content distribution network 100 (e.g., acontent delivery server 408), or using designated hardware and softwareresources within a shared content management server 102. The contentdelivery system 408 may receive content resources from the contentcustomization system 402 and/or from the user management system 404, andprovide the resources to user devices 106. The content delivery system408 may determine the appropriate presentation format for the contentresources based on the user characteristics and preferences, and/or thedevice capabilities of user devices 106. If needed, the content deliverysystem 408 may convert the content resources to the appropriatepresentation format and/or compress the content before transmission. Insome embodiments, the content delivery system 408 may also determine theappropriate transmission media and communication protocols fortransmission of the content resources.

In some embodiments, the content delivery system 408 may includespecialized security and integration hardware 410, along withcorresponding software components to implement the appropriate securityfeatures content transmission and storage, to provide the supportednetwork and client access models, and to support the performance andscalability requirements of the network 100. The security andintegration layer 410 may include some or all of the security andintegration components 208 discussed above in FIG. 2, and may controlthe transmission of content resources and other data, as well as thereceipt of requests and content interactions, to and from the userdevices 106, supervisor devices 110, administrative servers 116, andother devices in the network 100.

With reference now to FIG. 5, a block diagram of an illustrativecomputer system is shown. The system 500 may correspond to any of thecomputing devices or servers of the content distribution network 100described above, or any other computing devices described herein. Inthis example, computer system 500 includes processing units 504 thatcommunicate with a number of peripheral subsystems via a bus subsystem502. These peripheral subsystems include, for example, a storagesubsystem 510, an I/O subsystem 526, and a communications subsystem 532.

Bus subsystem 502 provides a mechanism for letting the variouscomponents and subsystems of computer system 500 communicate with eachother as intended. Although bus subsystem 502 is shown schematically asa single bus, alternative embodiments of the bus subsystem may utilizemultiple buses. Bus subsystem 502 may be any of several types of busstructures including a memory bus or memory controller, a peripheralbus, and a local bus using any of a variety of bus architectures. Sucharchitectures may include, for example, an Industry StandardArchitecture (ISA) bus, Micro Channel Architecture (MCA) bus, EnhancedISA (EISA) bus, Video Electronics Standards Association (VESA) localbus, and Peripheral Component Interconnect (PCI) bus, which can beimplemented as a Mezzanine bus manufactured to the IEEE P1386.1standard.

Processing unit 504, which may be implemented as one or more integratedcircuits (e.g., a conventional microprocessor or microcontroller),controls the operation of computer system 500. One or more processors,including single core and/or multicore processors, may be included inprocessing unit 504. As shown in the figure, processing unit 504 may beimplemented as one or more independent processing units 506 and/or 508with single or multicore processors and processor caches included ineach processing unit. In other embodiments, processing unit 504 may alsobe implemented as a quad-core processing unit or larger multicoredesigns (e.g., hexa-core processors, octo-core processors, ten-coreprocessors, or greater.

Processing unit 504 may execute a variety of software processes embodiedin program code, and may maintain multiple concurrently executingprograms or processes. At any given time, some or all of the programcode to be executed can be resident in processor(s) 504 and/or instorage subsystem 510. In some embodiments, computer system 500 mayinclude one or more specialized processors, such as digital signalprocessors (DSPs), outboard processors, graphics processors,application-specific processors, and/or the like.

I/O subsystem 526 may include device controllers 528 for one or moreuser interface input devices and/or user interface output devices 530.User interface input and output devices 530 may be integral with thecomputer system 500 (e.g., integrated audio/video systems, and/ortouchscreen displays), or may be separate peripheral devices which areattachable/detachable from the computer system 500.

Input devices 530 may include a keyboard, pointing devices such as amouse or trackball, a touchpad or touch screen incorporated into adisplay, a scroll wheel, a click wheel, a dial, a button, a switch, akeypad, audio input devices with voice command recognition systems,microphones, and other types of input devices. Input devices 530 mayalso include three dimensional (3D) mice, joysticks or pointing sticks,gamepads and graphic tablets, and audio/visual devices such as speakers,digital cameras, digital camcorders, portable media players, webcams,image scanners, fingerprint scanners, barcode reader 3D scanners, 3Dprinters, laser rangefinders, and eye gaze tracking devices. Additionalinput devices 530 may include, for example, motion sensing and/orgesture recognition devices that enable users to control and interactwith an input device through a natural user interface using gestures andspoken commands, eye gesture recognition devices that detect eyeactivity from users and transform the eye gestures as input into aninput device, voice recognition sensing devices that enable users tointeract with voice recognition systems through voice commands, medicalimaging input devices, MIDI keyboards, digital musical instruments, andthe like.

Output devices 530 may include one or more display subsystems, indicatorlights, or non-visual displays such as audio output devices, etc.Display subsystems may include, for example, cathode ray tube (CRT)displays, flat-panel devices, such as those using a liquid crystaldisplay (LCD) or plasma display, light-emitting diode (LED) displays,projection devices, touch screens, and the like. In general, use of theterm “output device” is intended to include all possible types ofdevices and mechanisms for outputting information from computer system500 to a user or other computer. For example, output devices 530 mayinclude, without limitation, a variety of display devices that visuallyconvey text, graphics and audio/video information such as monitors,printers, speakers, headphones, automotive navigation systems, plotters,voice output devices, and modems.

Computer system 500 may comprise one or more storage subsystems 510,comprising hardware and software components used for storing data andprogram instructions, such as system memory 518 and computer-readablestorage media 516. The system memory 518 and/or computer-readablestorage media 516 may store program instructions that are loadable andexecutable on processing units 504, as well as data generated during theexecution of these programs.

Depending on the configuration and type of computer system 500, systemmemory 318 may be stored in volatile memory (such as random accessmemory (RAM) 512) and/or in non-volatile storage drives 514 (such asread-only memory (ROM), flash memory, etc.) The RAM 512 may contain dataand/or program modules that are immediately accessible to and/orpresently being operated and executed by processing units 504. In someimplementations, system memory 518 may include multiple different typesof memory, such as static random access memory (SRAM) or dynamic randomaccess memory (DRAM). In some implementations, a basic input/outputsystem (BIOS), containing the basic routines that help to transferinformation between elements within computer system 500, such as duringstart-up, may typically be stored in the non-volatile storage drives514. By way of example, and not limitation, system memory 518 mayinclude application programs 520, such as client applications, Webbrowsers, mid-tier applications, server applications, etc., program data522, and an operating system 524.

Storage subsystem 510 also may provide one or more tangiblecomputer-readable storage media 516 for storing the basic programmingand data constructs that provide the functionality of some embodiments.Software (programs, code modules, instructions) that when executed by aprocessor provide the functionality described herein may be stored instorage subsystem 510. These software modules or instructions may beexecuted by processing units 504. Storage subsystem 510 may also providea repository for storing data used in accordance with the presentinvention.

Storage subsystem 300 may also include a computer-readable storage mediareader that can further be connected to computer-readable storage media516. Together and, optionally, in combination with system memory 518,computer-readable storage media 516 may comprehensively representremote, local, fixed, and/or removable storage devices plus storagemedia for temporarily and/or more permanently containing, storing,transmitting, and retrieving computer-readable information.

Computer-readable storage media 516 containing program code, or portionsof program code, may include any appropriate media known or used in theart, including storage media and communication media, such as but notlimited to, volatile and non-volatile, removable and non-removable mediaimplemented in any method or technology for storage and/or transmissionof information. This can include tangible computer-readable storagemedia such as RAM, ROM, electronically erasable programmable ROM(EEPROM), flash memory or other memory technology, CD-ROM, digitalversatile disk (DVD), or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or other tangible computer readable media. This can also includenontangible computer-readable media, such as data signals, datatransmissions, or any other medium which can be used to transmit thedesired information and which can be accessed by computer system 500.

By way of example, computer-readable storage media 516 may include ahard disk drive that reads from or writes to non-removable, nonvolatilemagnetic media, a magnetic disk drive that reads from or writes to aremovable, nonvolatile magnetic disk, and an optical disk drive thatreads from or writes to a removable, nonvolatile optical disk such as aCD ROM, DVD, and Blu-Ray® disk, or other optical media.Computer-readable storage media 516 may include, but is not limited to,Zip® drives, flash memory cards, universal serial bus (USB) flashdrives, secure digital (SD) cards, DVD disks, digital video tape, andthe like. Computer-readable storage media 516 may also include,solid-state drives (SSD) based on non-volatile memory such asflash-memory based SSDs, enterprise flash drives, solid state ROM, andthe like, SSDs based on volatile memory such as solid state RAM, dynamicRAM, static RAM, DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, andhybrid SSDs that use a combination of DRAM and flash memory based SSDs.The disk drives and their associated computer-readable media may providenon-volatile storage of computer-readable instructions, data structures,program modules, and other data for computer system 500.

Communications subsystem 532 may provide a communication interface fromcomputer system 500 and external computing devices via one or morecommunication networks, including local area networks (LANs), wide areanetworks (WANs) (e.g., the Internet), and various wirelesstelecommunications networks. As illustrated in FIG. 5, thecommunications subsystem 532 may include, for example, one or morenetwork interface controllers (NICs) 534, such as Ethernet cards,Asynchronous Transfer Mode NICs, Token Ring NICs, and the like, as wellas one or more wireless communications interfaces 536, such as wirelessnetwork interface controllers (WNICs), wireless network adapters, andthe like. Additionally and/or alternatively, the communicationssubsystem 532 may include one or more modems (telephone, satellite,cable, ISDN), synchronous or asynchronous digital subscriber line (DSL)units, FireWire® interfaces, USB® interfaces, and the like.Communications subsystem 536 also may include radio frequency (RF)transceiver components for accessing wireless voice and/or data networks(e.g., using cellular telephone technology, advanced data networktechnology, such as 3G, 4G or EDGE (enhanced data rates for globalevolution), WiFi (IEEE 802.11 family standards, or other mobilecommunication technologies, or any combination thereof), globalpositioning system (GPS) receiver components, and/or other components.

The various physical components of the communications subsystem 532 maybe detachable components coupled to the computer system 500 via acomputer network, a FireWire® bus, or the like, and/or may be physicallyintegrated onto a motherboard of the computer system 500. Communicationssubsystem 532 also may be implemented in whole or in part by software.

In some embodiments, communications subsystem 532 may also receive inputcommunication in the form of structured and/or unstructured data feeds,event streams, event updates, and the like, on behalf of one or moreusers who may use or access computer system 500. For example,communications subsystem 532 may be configured to receive data feeds inreal-time from users of social networks and/or other communicationservices, web feeds such as Rich Site Summary (RSS) feeds, and/orreal-time updates from one or more third party information sources(e.g., data aggregators 309). Additionally, communications subsystem 532may be configured to receive data in the form of continuous datastreams, which may include event streams of real-time events and/orevent updates (e.g., sensor data applications, financial tickers,network performance measuring tools, clickstream analysis tools,automobile traffic monitoring, etc.). Communications subsystem 532 mayoutput such structured and/or unstructured data feeds, event streams,event updates, and the like to one or more data stores 104 that may bein communication with one or more streaming data source computerscoupled to computer system 500.

Due to the ever-changing nature of computers and networks, thedescription of computer system 500 depicted in the figure is intendedonly as a specific example. Many other configurations having more orfewer components than the system depicted in the figure are possible.For example, customized hardware might also be used and/or particularelements might be implemented in hardware, firmware, software, or acombination. Further, connection to other computing devices, such asnetwork input/output devices, may be employed. Based on the disclosureand teachings provided herein, a person of ordinary skill in the artwill appreciate other ways and/or methods to implement the variousembodiments.

With reference now to FIG. 6, a block diagram is shown illustrating anexample of a mobile device session analyzer system 600. As shown in thisexample, a mobile device session analyzer system 600 may include one ormore mobile devices 610 configured to communicate with a mobile devicesession analyzer 620. As discussed below, mobile devices 610 may beconfigured to receive and execute content resources via their respectiveinput/output (I/O) subsystems 611. As used herein, a content resourceexecution session may refer to a continuous time period during which oneor more content resources are executed on a mobile device 610. Duringsuch content resource execution sessions, a user of the mobile device610 may consume (e.g., watch, read, play, etc.) the content resources,and may provide feedback relating to the content resources via the I/Osubsystem 611. Mobile devices 610 may be configured to receive such userfeedback and other relevant performance data associated with contentresource execution sessions. The user feedback data and otherperformance data associated with content resource execution sessions maybe received and/or determined before, during, or after the associatedexecution sessions. Mobile devices 610 also may be configured to detectand/or determine (e.g., using device sensors 612 and/or CPU 613) contextdata associated with specific content resource execution sessions. Suchcontext data may include, for example, device location, session time,session length, network data, movement and noise data, userbiostatistics data, data received from other mobile device applications,and the like. Mobile devices 610 may store the performance data andcontext data associated with content resource execution sessions, forexample, in local data stores 614, and also may transmit such data toone or more session analyzers 620. As discussed in more detail below,session analyzers 620 may include server components and/or processingengines, along with specialized data storage, networking and hardwarecomponents, configured to receive and analyze content resource executionsession data from the mobile devices 610, and to determine performanceconditions for associated users.

In order to perform these features and other functionality describedherein, each of the components and sub-components discussed in theexample mobile device session analyzer system 600 may correspond to asingle computer server or a complex computing system including acombination of computing devices, storage devices, network components,etc. Each of these components and their respective subcomponents may beimplemented in hardware, software, or a combination thereof. Certainmobile devices 610 may communicate directly with the session analyzer620, while other mobile devices 610 may communicate with the sessionanalyzer 620 indirectly via one or more intermediary network components(e.g., routers, gateways, firewalls, etc.) or other devices (e.g.,content management servers 102, content servers 112, etc.). Although thephysical network components have not been shown in this figure so as notto obscure the other elements depicted in the figure, it should beunderstood that any of the network hardware components and networkarchitecture designs may be implemented in various embodiments tosupport communication between the servers and devices in the system 600.Additionally, different mobile devices 610 may use different networksand networks types to communicate with the session analyzer 620,including one or more telecommunications networks, cable networks,satellite networks, cellular networks and other wireless networks, andcomputer-based IP networks, and the like. Further, certain componentswithin mobile device session analyzer system 600 may include specialpurpose hardware devices and/or special purpose software, such as thoseincluded in I/O subsystems 611 and sensor systems 612 of the mobiledevices 610, as well as those within the processing engines and datastores 621-624 of the session analyzer 620, discussed below.

In some embodiments, a mobile device session analyzer system 600 may beintegrated within, or configured to operate in collaboration with, oneor more content distribution networks 100. For example, system 600 maybe the same as, or may operate within or in collaboration with, any ofthe content distribution network (CDNs) 100 described above. Thus,specific examples of mobile device session analyzer systems 600 mayinclude, without limitation, educational and professional trainingsystems and networks, interactive gaming systems and networks, mediadistribution systems and networks, and enterprise application systemsand networks, websites and other Internet-based systems and networks. Insuch cases, the mobile device session analyzer 620 may be implementedwithin one or more content servers 112, content management servers 102,and/or data store servers 104, and mobile devices 610 may correspond tothe user devices 106 and 110 described above in reference to CDN 100.Thus, within system 600 (which may also be referred to as CDN 600),mobile devices 610 may request and receive content resources from thesession analyzer 620, execute the content resources using the hardwareand software components of the user devices 610, and then transmitvarious user interaction data back to the session analyzer 620. In otherexamples, session analyzer 620 may be implemented using one or morecomputer servers, and other specialized hardware and softwarecomponents, separately from other CDN components such as content servers112, content management servers 102, data store servers 104, and thelike. In these examples, the session analyzer 620 may be configured tocommunicate directly with mobile devices 610, or indirectly throughcontent management servers 102 and/or other components andcommunications networks of the CDN 600.

As discussed below, system 600 and other embodiments described hereinmay be used to execute content resources on user devices 610, receiveuser inputs via user devices 610 during content resources executionsessions, determine performance measurements and/or corresponding usercontexts associated with content resources execution sessions, andanalyze content resources execution sessions in order to determineperformance conditions for users within the system 600. Contentresources may refer to any digital content, such as media content (e.g.,music, movies, television programming, audiobooks, advertisements,etc.), gaming software, professional training and eLearning resources(e.g., courses, texts, lectures, interactive modules, tests andevaluations, etc.), as well as websites and other web-based content.Various types of content resources may be transmitted to, stored on, andexecuted by mobile devices 610 as files, executable software, services,and the like. Users may consume (e.g., view, read, listen to, play,etc.) content resources via compatible mobile devices 610 using thehardware and software resources on the mobile device 610. In someembodiments, the content resources may include interactive resources,such as interactive media, games, or professional training or eLearningcontent modules, which may be designed to elicit user responses orfeedback before, during, or after the execution of the content.

Mobile devices 610 may include laptop computers, smartphones, tabletcomputers, and other various types of mobile devices, each of which mayinclude some or all of the hardware, software, and networking componentsdiscussed above. Specifically, a mobile device 610 may be any computingdevice with sufficient memory for storing one or more content resources,and sufficient processing and I/O subcomponents for executing thecontent resources. As discussed above, such content resources mayinclude television programming, music, movies, lectures or materials ina training course or eLearning system, and/or gaming content.Accordingly, mobile devices 610 may include the necessary hardware andsoftware components to establish the network interfaces, security andauthentication capabilities, and content caching capabilities to receivethe content, store the content, and execute the content to provide tousers in real-time or at later time. Moreover, in certain embodiments, asingle mobile device 610 may have different context data (e.g., locationdata, network connectivity status data, movement and noise data, etc.)during different content resource execution sessions. Laptop computers,tablet computers, smart phones, smart watches, wearable computingdevices, and vehicle-based computing systems are all examples of mobiledevices 610 that may change locations and network connectivity status,may detect movement and noise data, and may have other changing contextdata during a single content resource execution session or betweenmultiple different execution sessions.

In this example, mobile devices 610 each include an I/O subsystem 611,one or more device sensors 612, a processing unit 613, a data store 614,and a network interface controller 615. As discussed above, each mobiledevice 610 may be configured to receive and execute content resourcesusing their respective I/O subsystems 611. Each I/O subsystem 611 mayinclude hardware and software components to support a specific set ofoutput capabilities (e.g., LCD display screen characteristics, screensize, color display, video driver, speakers, audio driver, graphicsprocessor and drivers, etc.), and a specific set of input capabilities(e.g., keyboard, mouse, touchscreen, voice control, cameras, facialrecognition, gesture recognition, etc.). Different mobile devices 610may support different input and output capabilities within their I/Osubsystems 611, and thus different types of content resources may becompatible or incompatible with certain mobile devices 610. For example,certain content resources may require specific types of processors,graphics components, and network components in order to be optimallyexecuted on a mobile device 610. Additionally or alternatively, variouscontent resources may require specific output capabilities (e.g., LCDdisplay screens, minimum screen sizes, color displays, video, audio,graphics, etc.) and/or specific input capabilities (e.g., keyboard,mouse, touchscreen, voice control, gesture recognition, etc.) in orderto be optimally executed on a mobile device 610. In some embodiments,users may establish user-specific preferences for executing specifictypes of content resources on specific types of user devices.

Each mobile device 610 also may include one or more device sensors 612configured to detect context data associated with specific contentresource execution sessions. Context data may include any datadescribing the current (and/or previous) state of the mobile device 610,the physical environment of the mobile device 610, and/or the user ofthe mobile device 610, at the time of a content resource executionsession. For example, such context data may include the location of themobile device 610 and any detected movement of the mobile device 610during a content resource execution session, including speed and overalldistance travelled, as well jiggling and vibrating movements indicativeof walking, jogging, running, or traveling in cars, busses, or trains,etc. Accordingly, sensors 612 may include accelerometers, speedometers,compasses, gyroscopes, and/or digital positioning systems such as GlobalPosition Satellite (GPS) receivers, in order to detect the position andmovement of the device 610 during an execution session. Additionalcontext data may include the orientation of the mobile device 610,ambient noise and/or visual background data detected by the device 610,and temperature and lighting data within the physical environment of themobile device 610 during an execution session. Thus, sensors 612 alsomay include thermometers, barometers, light sensors, cameras,microphones, heat sensors, motion sensors, and the like, in order todetect background noises such as traffic, music, conversations, andother potential distractions (e.g., other people nearby, animals, etc.),as well as lighting and temperature factors that may affect performanceduring an execution session.

In some embodiments, device sensors 612 may include user health andactivity sensors, such as heartrate and blood pressure sensors, sleepmonitors, and personal exercise/fitness sensors that may detect andtrack the physical state and condition of the user before and during acontent resource execution session. For instance, a mobile device 610may be a personal and/or wearable computing device configured to detectcurrent health and activity data of a user, and then transmit thebiostatistics data for the user to the session analyzer 620 and/or othermobile devices 610 within the system 600. As described below, suchbiostatistics data, like other session context variables, may be storedand correlated with user performance measurements during contentresource execution sessions to determine performance conditions for theuser.

It should be understood that the above examples of specific sensors 612are illustrative and non-limiting only, and that any other mobile devicesensor 612 may be activated during content resource execution sessionsto detect and record data that may be used to determine user performanceconditions based on correlations between user performance measurementsand sensor readings during execution sessions. Additionally, asdescribed below, certain types of context data might not requirespecialized device sensors 612, and thus such sensors 612 may beoptional in some embodiments. For example, the context data associatedwith a content resource execution session may include session time,session length, and current device capabilities and status data such asprocessor status and availability, memory usage and availability,network availability, etc. Additional context data may be received fromother applications executing on the mobile device 610 and/or otherrelated user devices 610. For instance, if a user recently orconcurrently activated and/or interacted with certain softwareapplications (e.g., a mobile phone application, music application,gaming application, web browser, etc.) during a content resourceexecution session, then the user's interactions may be stored as contextdata which may correlate positively or negatively to the user'sperformance during the execution session. In addition to applicationlaunch states, additional context information may be received fromprofiles built by applications granted security permissions, as well asphone operating system-level services, from various mobile device andmobile software providers (e.g., GOOGLE, APPLE, MICROSOFT, etc.).Additionally, mobile assistant services (e.g., SIRI, GOOGLE NOW,CORTANA, etc.) also may serve as a potentially rich user profile contextsource.

After collecting various session data for one or more content resourceexecution sessions, such as session context variable data and userperformance and/or user feedback data, mobile devices 610 may store thesession data in a local data store 614 or transmit the session data viaa network interface 615 to a mobile device session analyzer 620. Asshown in FIG. 6, mobile device session analyzer 620 may receive datarelating to multiple content resource execution sessions from multipledifferent mobile devices 610. The session analyzer 620 may be configuredto collect and store mobile device data and session data in one or moredata stores 622 and 623. The session analyzer 620 may include one ormore processing engines 621 and 624 configured to analyze the sessiondata received from the mobile devices 610 and determine performanceconditions for users associated with the session data (e.g., sessionanalyzer engine 621), as well as monitoring the context data of themobile devices 610 against the user's performance conditions to providenotifications that a user's current context data matches the performanceconditions determined for the user (e.g., notification engine 624). Thesession analyzer engine 621, notification engine 624, and data stores622-623 may be implemented as separate software (and/or storage)components within a single computer server 620 in some examples, whilein other examples may be implemented as separate computerservers/systems having separate dedicated processing units, storagedevices, and/or network components.

Referring now to FIGS. 7A and 7B, two tables are shown including examplemobile device data (FIG. 7A) and example content resource executionsession data (FIG. 7B) that may be illustrative of certain embodimentsof the disclosure. In this example, FIG. 7A represents an example mobiledevice table 710 that may be stored in a device data store 622 of amobile device session analyzer 620. Table 710 may store a list of devicecapabilities and/or characteristics for one or more mobile devices 610within a mobile device session analyzer system 600. For example, table710 (and/or other tables 710 within a data store 622) may store anyhardware and software components and capabilities of the mobile devices610 (processors, memory systems, network capabilities, drivers, clientapplications, etc.), the input/output devices 611 and capabilities(e.g., integrated and peripheral I/O devices, I/O software, I/Ocapabilities, etc.), as well as any device sensors 612 and sensorcapabilities. In some examples, session analyzer 620 and/or othercomponents with a CDN 600 may perform a registration process for newmobile devices 610, during which a mobile device 610 may provide itsdevice components, characteristics, and/or capabilities to be enrolledwithin the CDN and/or session analyzer system 600. In other examples,mobile devices 610 may transmit device characteristics and capabilitiesdata along with transmissions of content resource execution sessiondata, and the session analyzer 620 may extract the data and update table710 with the received device data. In either case, mobile devices 610and session analyzers 620 may be respectively configured to transmit andreceive/store updates to the device data for a mobile device 610. Forinstance, updated device data may be transmitted by a mobile device 610in response to hardware or software upgrades to the mobile device 610,or the installation or removal of a peripheral I/O device 611, sensor612, etc. The session analyzer 620 may receive device data updates frommobile devices 610 and update device data table 710 as needed.

FIG. 7B represents an example mobile device session table 720 that maybe stored in a session data store 623 of a mobile device sessionanalyzer 620. Session data store 623 may include various data tables 720containing data relating to content resource execution sessionsperformed by users via mobile devices 610. As shown in this example,mobile device session table 720 (and/or other tables 710 within datastore 623) may store, for each content resource execution session, asession identifier, a user identifier (i.e., corresponding to the userthat initiated the content resource execution session), a deviceidentifier (i.e., corresponding to the mobile device 610 on which theuser content resource session was executed), and one or more contentresource identifiers (i.e., corresponding to the specific contentresource(s) executed during the session). The table 720 also may includeone or more context data associated with each content resource executionsession, such as session time, session length, session location, and/orany of the additional context data discussed herein for content resourceexecution sessions. Finally, example table 720 includes sessionperformance data corresponding to one or more performance measurementsof the user associated with the content resource execution sessions.Such performance measurements, discussed in detail below, may be basedon data such as user feedback, user interactions, user consumptionvelocities and remediation rates, etc.

Referring now to FIG. 8, an example diagram is shown illustrating asequence of data transmissions from mobile devices 810 to a mobiledevice session analyzer 820, where each data transmission may includedata relating to a content resource execution session performed by auser on the mobile device 810. The architecture and hardware/softwarecomponents of system 800 may be similar (or identical) to those insystem 600, discussed above. For example, each mobile device 810 maycorrespond to a mobile device 610, and session analyzer 820 maycorrespond to session analyzer 620. However, FIG. 8 illustrates specificexamples of different mobile devices 810 associated with a user, andspecific examples of transmitting execution session data from the mobiledevices 810. In this case, a user may use five different mobile devices810 at various different times to execute content resources: asmartphone 810 a, a smartwatch 810 b, a tablet computer 810 c, avehicle-based computer system 810 d, and a laptop computer 810 e. Asdiscussed above, each mobile device 810 may have different devicecharacteristics and capabilities, which may be stored by the individualdevices 810 and/or within a data store of the session analyzer 820.

FIG. 8 also illustrates a sequence of data transmissions (1-9) from theindividual mobile devices 810 to the mobile device session analyzerserver 820. Each data transmission (1-9) may contain informationdescribing one or more content resource execution sessions performed bya user on the mobile device 810. The data transmitted from mobiledevices 810 during data transmissions (1-9) may include similar data tothat discussed above in reference to FIG. 7B, for example, useridentifiers, device identifiers, content resource identifiers, contextdata in the form of session context variable and value pairs (e.g.,session time and value, session length and value, session location andvalue, network type and value, network speed and value, etc.), and/orsession performance data indicating performance measurements of the userduring the content resource execution sessions. As illustrated in thisexample, the context data for each mobile device 810 may change overtime, as the mobile devices 810 may change locations, users, networks,etc. Thus, each data transmission (1-9) may include a unique combinationof device data, user data, time data, location data, and/or networkdata, as well as additional unique context data and session performancedata.

Referring now to FIG. 9, a flow diagram is shown illustrating a processof determining one or more performance conditions associated with auser, based on a user's content resource execution sessions. Asdescribed below, the steps in this process may be performed by one ormore components in the mobile device session analyzer systems 600described above, such as a mobile device 610 and/or a session analyzerserver 620. Prior to the steps of FIG. 9, discussed below, a mobiledevice 610 may request and receive a set of content resources, forexample, from a content management server 102 or content server 112(either of which may be implemented within a session analyzer server620), or other content repository. Content resources may include anydigital content that may be executed on a user device 610, such as mediacontent (e.g., music, movies, television programming, audiobooks,advertisements, etc.), gaming software, professional training andeLearning resources (e.g., online courses, texts, video lectures,interactive software modules, tests and evaluations, etc.), as well aswebsites and other web-based content. Different types of contentresources may be transmitted to, stored on, and executed by mobiledevices 610 as files, executable software, services, and the like.

During the execution of one or more content resources by a user, whichmay be referred to as a content resources execution session, the usermay consume (e.g., view, read, listen to, play, etc.) and interact withthe content resources using the hardware and software components oftheir mobile devices 610 (e.g., I/O subsystems 611). As discussed above,different mobile devices 610 may have different I/O subsystems 611 andother hardware, software, and network differences that support differenttypes of resource consumption and resource interaction behaviors byusers.

Additionally, during a content resource execution session, a mobiledevice 610 may collect and store various data relating to the executionsession. For example, the mobile device 610 may store basic sessiondata, such as user that requested and executed the resources, thespecific resources executed, the session time, etc. The mobile device610 also may detect and store various context data during executionsessions, including the location of the mobile device 610 and otherphysical environment data (e.g., movement data, noise data, lightingdata, temperature data, etc.), user biostatistics data (e.g., heartrate,blood pressure, sleep data, diet data, exercise/fitness data, etc.),data received from other applications on the mobile device 610 or otheruser devices 610 (e.g., phone application data, music application data,gaming data, web browsing data, etc.), as well as other sensor data andany additional context data discussed herein.

The mobile device 610 also may collect and store user feedback and otheruser interaction data during execution sessions. User feedback and userinteraction data may be received via the I/O subsystem 611 of the mobiledevice 610 executing the content, or in other cases may be received viathe input and output components of a different user device. For example,in some embodiments, content may be executed/played on one device (e.g.,a television, classroom or conference room projector, audio system,etc.), and the user may interact with the content and provides feedbackvia a different device (e.g., a smartphone, personal tablet or laptop,etc.). The user interaction data collected and stored by the mobiledevice 610 during an execution session may include user selections ofcontent resources (e.g., starting, stopping, pausing, skipping forwardor back, replaying sections, etc.), user responses todecision/navigation points within interactive user content resources,user behaviors while consuming content resources (e.g., text inputs,audio responses, gestures, facial expressions, body language, etc.),scores of user interactions (e.g., user scores of game levels, eLearningmodules, tests or evaluations, etc.), and/or the user's answers toexplicit requests for feedback or evaluations of content resources. Suchuser interaction data may be referred to as clickstream processing insome cases. Additional user interaction data may include data metricsrelating to a user's interaction with the content, such as amount oftime taken for the user to make a selection, the number ofselections/attempts the user makes at a given navigation point, and anyaids, tools, or help that the user used when interacting with thecontent.

In some embodiments, some or all of the data collected and stored bymobile devices 610 during content resource execution sessions, includingsession data, context data, and/or user interaction data, etc., may betransmitted by the mobile devices 610 to the session analyzer 620 duringor after the execution sessions, as shown in FIG. 8. In suchembodiments, the session analyzer 620 may receive content resourceexecution session data from multiple devices 610, and may perform thesteps of FIG. 9 on the aggregated data from multiple devices 610. Inother embodiments, the mobile devices 610 may perform certain steps andanalyses, such as user performance measurements, evaluations of contextdata to identify potential distractions and other relevant factors,before transmitting data to the session analyzer 620. In still otherexamples, each mobile device 610 may perform each of the steps and FIG.9 individually, without any communication with a session analyzer server620. The mobile device session analyzer 620 may be optional in suchcases, and mobile devices 610 may communicate directly with each other,or need not communicate at all and each mobile device 610 may determineits own device-specific performance conditions for the user.

In step 901, data relating to one or more content resource executionsessions may be received, for example, by a mobile device sessionanalyzer 620 from one or more mobile devices 610. As discussed above,the data received in step 901 may include session data (e.g., useridentifier, resource identifiers, execution times, etc.), various typesof context data (e.g., location data, physical environment data, userbiostatistics data, data received from other applications, etc.), userinteraction data received by the mobile device 610, and any other datacollected in connection with an execution of content resources on themobile device 610.

In step 902, one or more user performance measurements may be determinedfor the content resource execution session. In some embodiments, amobile device 610 and/or mobile device session analyzer 620 maycalculate user performance with respect to content resource executionsessions based on the user interaction data received in step 901.Several different types and techniques of performance measurements maybe determined in different embodiments and/or based on different typesof content resources. In some cases, a performance measurement maycorrespond to a user score or evaluation. For example, gaming software,professional training or eLearning software, and other content resourcesmay calculate user scores for game levels, comprehension levels ofeLearning modules, automated online tests, etc. User scores forinteractive content resources may be calculated during the execution ofthe resources (e.g., for an interactive game) or after the completion ofthe execution session (e.g., for a training/eLearning module), and insome cases the evaluation/scoring process may be performed at adifferent mobile device 610 then the device executing the resources.

Other types of performance measurement that may be determined in step902 may include express feedback from the user regarding the contentresources, such as user content ratings, discussion posts, contentevaluations, and the like. For instance, certain CDNs 100 and/orspecific content resources may solicit user ratings during or afterexecution of the content (e.g., movie and television program ratings,game reviews, training/eLearning module ratings, course ratings,instructor ratings, etc.). Additional user feedback that may becollected for performance measurements may include the amount of timethe user played/executed the resources, a record of the user decisionsand other interactions during the execution of the resources, and audioand/or visual cues (e.g., voice feedback, facial expressions, gestures,body language, etc.) which may be collected and stored by the mobiledevice 610 during the execution of the content resources.

Additionally, in some embodiments, the velocity and/or the remediationrate of a user during one or more content resource execution sessionsmay be determined and used as a user performance measurement in step902. Consumption velocity may refer to the speed at which a userconsumes content resources, and remediation rate may refer to the rateat which the user returns to previously consumed/executed content duringthe execution session. To illustrate, a first user who quickly consumesand completes one or more media resources, game levels, eLearningmodules, and the like, may be assigned a high consumption velocity forthe content resource execution session, whereas a second user whoproceeds slowly through the content resources (e.g., frequently pausing,repeating portions or sections multiple times, selecting all possiblechoices or answers in an interactive resource, etc.) may be assigned alow consumption velocity. However, if the first user (or another user)returns frequently to previously viewed/executed resources, then thefirst user may be assigned a high remediation rate, whereas if thesecond user (or another user) rarely returns to a content resource aftercompleting it, then the second user may be assigned a low remediationrate. Consumption velocities and/or remediation rates for a user duringone or more execution sessions may be calculated based on the overalltimes required to complete resources, the numbers of userdecisions/interactions during execution sessions, and/or numbers orrates of resource consumption, etc.

In step 903, one or more items of context data may be determined for thecontent resource execution session, based on the data received in step901. In some embodiments, context data may be collected and determinedby one or more mobile devices 610, a mobile device session analyzer 620,or a combination of mobile devices 610 and session analyzers 620. Thecontext data determined in step 903 may include any of the various typesof context data discussed above, for example, device location data,device movement data, data relating to the physical environment of thedevice 610 (e.g., noise, lighting, other distractions), userbiostatistics data, data received from other software applicationsrelating to mobile device 610 or the user.

In some examples, the mobile device 610 may detect certain raw contextdata using device sensors 612, such as location data, movement data,noise data, image data, user biostatistics data, and the like, and thentransmit the raw context data to the session analyzer 620 for analysisand classification. For instance, the mobile device 610 may collect andtransmit raw time data corresponding to a content resource executionsession (e.g., start time, stop time, user interaction times), and thesession analyzer 620 may use the raw time data to classify the executionsession into one or more time ranges (e.g., morning, afternoon, evening,etc.). Similarly, the mobile device 610 may collect and transmit rawlocation data for an execution session, and the session analyzer 620 mayanalyze the raw execution data to determine a location or location(e.g., home, work, school, library, vehicle, coffee shop, etc.). Thesession analyzer 620 also may analyze location and/or movement data(e.g., accelerometer readings, gyroscope readings, etc.) to determineuser activity context data (e.g., jogging, driving, bus, train, or airtravel, etc.). As another example, the mobile device 610 may collect andtransmit raw noise data, light data, and/or image data, and the sessionanalyzer 620 may analyze the data to identify distraction context data(e.g., ambient noise levels, music, background conversations, high/lowlighting conditions, etc.).

As illustrated in these examples, the mobile device session analyzer 620may receive and analyze raw context data from mobile devices 610, andthen group and/or classify the context data into ranges in order tocharacterize an execution session as having a particular context. Insome cases, the session analyzer 620 may determine context data pairs,each pair consisting of a session context variable (e.g., time,location, movement pattern, noise level, distractions, networkconnectivity, etc.) and a value or value range for the session contextvariable. Examples of values or value ranges for a time session contextvariable may include, for instance, 7:30 am, 2:00 pm-4:30 pm, weekdaymorning, Sunday afternoon, after school in summertime, holiday weekend,etc. Examples of values or value ranges for an ambient noise sessioncontext variable may include, for instance, silence, quiet backgroundmusic, background conversation, loud music, traffic noise, pet noise,etc. Additionally illustrative examples of session context variables andcorresponding values may be found in the first two columns of table 1010in FIG. 10A.

In some cases, the session analyzer 620 may determine certain types ofcontext data for a mobile device 610 without receiving any raw contextdata or other context information from the mobile device 610. Forexample, the relevant context data for an execution session may includethe capabilities and characteristics of the mobile device 610, which maybe stored in a device data store 622 (or other storage system) and neednot be transmitted by the mobile device 610. Additionally, the sessionanalyzer 620 may use some context data received from a mobile device610, and then access one or more external servers to determineadditional context data. For instance, location data received from amobile device may be used by the session analyzer 620 to access externaldata sources to determine characteristics about the location (e.g.,public or private, type of business, etc.), along with current weatherconditions at the location, traffic and road conditions at the location,and the like, so that the mobile device 610 need not transmit thisadditional context data as well.

Also, for a content resource execution session performed on one mobiledevice 610 a, the session analyzer 620 may receive or retrieve contextdata from other mobile devices 610 b-610 d associated with the sameuser. For example, if a user executes a set of content resources on afirst mobile device 610 a that does not include certain device sensors611 (e.g., a GPS receiver, movement sensors, microphones, cameras,etc.), then another mobile device 610 b located near the first device610 a may be activated to detect, store, and transmit the relevantcontext data (e.g., location data, movement data, audio data,image/video data, etc.). In such cases, the other mobile device 610 bmay transmit the context data to the first mobile device 610 a, ordirectly to the session analyzer 620. Additionally, certain softwareapplications currently running (or recently ran) on the user's otherdevices 610 b may provide relevant context data for an execution sessionon the first mobile device 610 a. For instance, if a user is executing aset of content resources on a first mobile device 610 a, while at thesame time using the telephone application, music player, gamingapplications, and/or web browser on the user's other devices 610 b-610d, then these devices may provide the relevant application informationto the session analyzer 620 as well. In some embodiments, the sessionanalyzer 620 may be configured to request and/or receive context datafrom any other user devices 610 positioned near the mobile device 610 aduring the same time window as an execution session.

As shown in FIG. 9, steps 901-903 may be repeated multiple times beforethe performance conditions for a user are calculated in step 904. Insome cases, a minimum threshold of content resource execution sessiondata, including both user performance data and session context data, maybe required before performance conditions can be calculated withstatistical reliability. Additionally, even after a set of performanceconditions is initially calculated for a user in step 904, the user maycontinue to perform content resource execution sessions on the user'smobile devices 610. In such cases, steps 901-903 may continue to beperformed for any newly received execution session data, and step 904may be performed again to update the user's performance conditions basedon the newly received data.

In step 904, one or more performance conditions may be determined for auser, based on the content resource execution session data received andanalyzed in steps 901-903. As used herein, a performance condition for auser may refer to a statistical correlation between a value or range ofvalues of a session context variable, and a predicted effect on theuser's performance during content resource execution sessions. Forexample, a performance condition for a user may correlate a particulartime of day to a higher or lower level of performance by the user duringcontent resource execution sessions. Other example performanceconditions may correlate specific locations (or types of locations),movement data, background noise (e.g., types of noise and/or noiselevels), temperatures, etc., to higher or lower levels of performance bythe user during execution sessions.

Referring briefly to FIGS. 10A and 10B, two example tables are shownincluding illustrative performance condition data. FIG. 10A is anexample performance condition table 1010 listing a set of illustrativeperformance conditions for a user. In this example, each performancecondition listed in table 1010 includes a session context variable, avalue (or range of values) for the session context variable, and acorresponding predicted performance effect for the user. In thisexample, the user's performance during content resource executionsessions may be calculated on a point scale from 0 to 100. ThePerformance+/−column in table 1010 lists the predicted performanceincrease or decrease for the user, when the context of an executionsession is within the identified value/range for the identified contextvariable. For instance, when the user in this example executes contentresources on weekday mornings the user's predicted performance will be4.5 points higher than it otherwise would, and when the user executesthe content resources at home the user's predicted performance will be8.6 points higher than it otherwise would. However, when the userexecutes content resources in an environment with ambient noise rangingbetween 60-65 dB, the user's predicted performance will be 6.7 pointslower than it otherwise would, and when the user slept only 4-6 hoursthe previous night the user's predicted performance will be 2.0 pointslower than it otherwise would, and so on. It should be understood thatthe examples of performance conditions shown in FIG. 10A areillustrative only and non-limiting, and in various embodimentsperformance conditions may be based on any context data type, factor,and/or value or range discussed herein.

Certain performance conditions determined in step 904 may be applicableto individual users, while other performance conditions may beapplicable to groups of users, such as a group of family members,roommates, coworkers, or all users within a CDN 600. Additionally,certain performance conditions determined in step 904 may be applicableto specific CDNs 600 and/or specific types of resources within CDNs 600.For example, as shown in FIG. 10B, performance condition table 1010 mayinclude performance conditions determined based on an analysis of thecontent resource execution sessions of a single user (“User A”) within asingle gaming application (“Game ABC”) of an online gaming CDN 600. Asthis example illustrates, a single user may have different sets ofperformance conditions applicable to different types of CDN (e.g., mediadistribution CDNs, professional training/eLearning CDNs, gaming CDNs,etc.) and for different content resource types within one or more CDNs600.

In order to determine the performance conditions in step 904, thesession analyzer 620 (or mobile device 610) may execute statisticalanalysis techniques to identify a session context variable, isolate thevariable and the value or range of values for the variable, andcalculate the performance effect of the variable and value/range. Forexample, the session analyzer 620 may use regression analyses to controlfor the performance effects of other session context variables, therebyisolating a single variable and single value/range for the variable,while effectively holding constant the other possible variablesaffecting user performance during the execution sessions. After removingthe potential performance effects caused by other session contextvariables via regression analysis, the effect caused by one isolatedvariable may be calculated to determine the performance+/−of thatvariable. Similar regressions may be used to isolate analyze theperformance effect caused by all session context variables, andperformance effect calculations may be done for one or more differentvalues, groups, or ranges for each variable. Such calculations also maytake into account (e.g., control for) the difficulty of the contentresources executed during a session, based on performance data fromother users executing the same resources and/or the performance of theuser executing other similar resources.

In step 905, the performance conditions determined in step 904 may betransmitted to one or more user devices. In some cases, reportsincluding a listing of performance conditions may be generated andtransmitted to various client devices, as well asinstructor/administrator devices associated with the users. Thus, users,system administrators, instructors or teachers, and/or managers mayreceive performance condition data for users, allowing users of eachrole to adjust future behaviors relating to the presentation orconsumption of content resources. For example, a distributor orpresenter of online gaming content, certain media resources, or aprofessional training/eLearning resources may require users to usemobile devices having specific device capabilities, or to executeresources at certain times/places, etc., based on the determinedperformance conditions. Similarly, users consuming resources may alterconsumption patterns based on the determined performance conditions.Additionally, as discussed below in reference to FIGS. 11-14, after aset of performance conditions have been determined for a user, thecurrent context of the user and the user's devices 610 may be monitoredin order to provide notifications and suggestions to the user forexecuting certain content resources at certain times. In some suchembodiments, pairs of session context variables and values/ranges may betransmitted to individual mobile devices 610, so that the mobile devices610 may periodically test the received pairs of session contextvariables and values/ranges against the current context data of theuser, device, and environment.

Referring now to FIG. 11, a flow diagram is shown illustrating anexample process of determining a set of content resources based on thecurrent context data of a mobile device. As described below, the stepsin this process may be performed by one or more components in the mobiledevice session analyzer systems 600 described above, such as a sessionanalyzer server 620 and/or mobile device 610. Steps 1101-1105 may beperformed after the determination of performance conditions for one ormore users, based on analyses of previous content resource executionsessions by the users. As noted above, certain performance conditionsmay be user specific, CDN specific, resource type-specific, and/ordevice specific, while other performance conditions may apply tomultiple users, CDNs, resource types, and/or devices. Accordingly, theperformance conditions discussed in steps 1101-1105 may include bothuser-, CDN-, resource type-, and device-specific performance conditions,as well as performance conditions applying to multiple users, CDNs,resource types, and devices.

In step 1101, the session analyzer 620 may receive and/or detect acurrent context data of a mobile device 610. For example, the sessionanalyzer 620 may receive periodic transmissions of context data from amobile device 610 a. The session analyzer 620 may determine and/orretrieve additional context data for the mobile device 610 a using othertechniques described above, such as retrieving context data from localdata stores 622, other mobile devices 610, and/or external data sources.

In step 1102, the session analyzer 620 may compare the current contextdata of the mobile device 610 a to the previously determined performanceconditions associated with the user and/or the mobile device 610 a. Forinstance, if a user has one or more performance conditions based ontime, location, device movement, and background noise, then the sessionanalyzer 620 in step 1102 may compare the session context variablevalues for these performance conditions to the current context data ofthe user's mobile devices 610. In some cases, the session analyzer 620may sum (or otherwise combine) the anticipated performance effect formultiple different performance conditions. Referring again to exampletable 101, if the current context data received in step 1101 indicatesthat the current time is Tuesday at 10:00 am (+4.5), the user iscurrently travelling in his/her vehicle (−1.5), and current usinghis/her smartphone (−4.3), then the session analyzer 620 may sum thesematching performance conditions to determine an anticipated net negativeeffect (4.5−—−1.5−4.3=−1.3) on user performance for the current context.As another example, if the current context data received in step 1101indicates that the current time is Thursday at 8:00 am (+4.5), the useris currently at home (+8.6), and is current using a touchscreen device(+7.3), then the session analyzer 620 may sum these matching performanceconditions to determine an anticipated net positive effect(4.5+8.6+7.3=20.4) on user performance for the current context.

In step 1103, if the session analyzer 620 determines that overallcurrent context data of the user and/or mobile device 610 a correspondsto an anticipated net positive effect on user performance (1103:Yes),then the session analyzer 620 may determine a set of content resources(step 1104) and transmit a notification to the user's mobile device 610(step 1105), as discussed below. To the contrary, if the sessionanalyzer 620 determines that overall current context data of the userand/or mobile device 610 a corresponds to an anticipated net negativeeffect on user performance, or to an insufficiently net positive effectthat does not reach a minimum threshold (1103:No), then the sessionanalyzer 620 would not transmit a notification to the user's mobiledevice 610 but would return to step 1101 to await updated context datafrom the mobile device 610.

In step 1104, after determining that the current context data of theuser and/or mobile device 610 a corresponds to an anticipated netpositive effect on user performance, then the session analyzer 620 maydetermine one or more content resources to suggest to the user. In somecases, the session analyzer 620 may select the next content resource(s)in a sequence of content resources being executed by the user, such astelevision program episodes, sequential game levels, sequentialeLearning modules, etc. Additionally, as noted above, certainperformance conditions may be CDN-specific and/or resource type-specificperformance conditions. Therefore, the determination of contentresources in step 1104 may be performed by analyzing the subset ofperformance conditions relating to the specific CDN and/or resourcetype. For instance, referring again to FIGS. 10A-10B, a calculation ofan anticipated net positive effect on user performance in this examplemay be applicable only for User A, and only for Game ABC on the gamingCDN. Thus, steps 1103 and 1104 may include determining a highestanticipated net positive effect on user performance among different CDNsand/or resource types, based on the same set of current context data.

In step 1105, the session analyzer 620 may transmit a notification tothe user's mobile device 610 a indicating that the current context ofthe mobile device 610 a is correlated with high user performance. Forexample, email, text message, or application-based notifications may besent in real-time or near real-time to the user's mobile device 610 aand/or other nearby mobile devices 610. Such transmissions may indicateto the user that the current context data (e.g., user state, devicestate, physical environment, etc.) corresponds to generalhigh-performance conditions for the user, or may include one or moresuggestions of the specific content resources determined step 1104,which may have the highest anticipated performance conditions for theuser.

Referring briefly to FIG. 13, an example of a user interface screen 1310is shown notifying the user that the current context data for the userand/or mobile device 1300 is correlated with a high level of userperformance for executing content resources on the mobile device 1300.The notification 1310 also includes two suggestions of specific contentresources 1311 and 1312 that correspond to the highest anticipated userperformance conditions for the current context data.

Referring now to FIG. 12, another flow diagram is shown illustrating anexample process of determining a set of content resources based on thecurrent context data of a mobile device. The process shown in FIG. 12may be similar to the process described above in FIG. 11 in severalrespects. For example, the steps in this process may be performed by oneor more components in the mobile device session analyzer systems 600described above, such as a session analyzer server 620 and/or mobiledevice 610. Additionally, steps 1201-1205 may be performed after thedetermination of performance conditions for one or more users, based onanalyses of previous content resource execution sessions by the users.However, the example process shown in FIG. 12 may be initiated by theuser, for example, by instantiating and interacting with a CDN clientapplication on a mobile device 610.

In step 1201, a request may be received by a session analyzer 620 from amobile device indicating that a user intends to initiate a contentresource execution session on the mobile device 610. For example, a usermay instantiate and/or activate a CDN client application on a mobiledevice 610, such as a web browser, media player, gaming application,professional training or eLearning client, or any other CDN clientapplication. In some cases, the user may expressly request a suggestionof one or more content resources for the user's current executionsession on the mobile device 610.

In step 1202, in response to the user-initiated request, the sessionanalyzer 620 may retrieve and determine the current context data of themobile device 610. Step 1202 may be similar or identical to step 1101discussed above. For example, the session analyzer 620 may request andreceive a transmission of context data from a mobile device 610. Thesession analyzer 620 also may retrieve additional context data for themobile device 610 using the other techniques discussed above, such asretrieving context data from local data stores 622, other mobile devices610, and/or external data sources.

In step 1203, the session analyzer 620 may compare the current contextdata of the mobile device 610 to the previously determined performanceconditions associated with the user and/or the mobile device 610. Step1203 may be similar or identical to step 1102 discussed above. Forinstance, if a user has one or more performance conditions based ontime, location, device movement, and background noise, then the sessionanalyzer 620 in step 1203 may compare the session context variablevalues for these performance conditions to the current context data ofthe user's mobile device 610. The session analyzer 620 also may sum (orotherwise combine) the anticipated performance effect for multipledifferent performance conditions, as discussed above.

In step 1204, the session analyzer 620 may determine one or more sets ofcontent resources to suggest to the user. Step 1204 may be similar oridentical to step 1104 discussed above. For example, the sessionanalyzer 620 may select the next content resource(s) in a sequence ofcontent resources being executed by the user, such as television programepisodes, sequential game levels, sequential eLearning modules, etc. Insome cases, the session analyzer 620 be performed by analyzing thesubset of performance conditions relating to multiple different CDNsand/or resource types, in order to determine the highest anticipated netpositive effect on user performance among different the CDNs and/orresource types, based on the same set of current context data, asdiscussed above.

In step 1205, the session analyzer 620 may transmit the suggestions ofthe specific content resources determined step 1204 to the user's mobiledevice 610 for presentation to the user. Step 1205 may be similar oridentical to step 1105 discussed above. In various examples, the sessionanalyzer 620 may transmit the determined content resource suggestionsvia email, text message, or application-based notifications, and thesuggestions may be ranked in some cases in order of the highestanticipated net positive effect on user performance.

Referring briefly to FIG. 14, another example of a user interface screen1410 is shown on a mobile device 1400, providing multiple contentsuggestions in response to the user-initiated initiation that the usermay wish to perform a content resource execution session. In this case,three content resource suggestions 1411-41413 have been determined basedon the current context data of the mobile device 1400, including thecurrent context state of the mobile device, the user, and the physicalenvironment of the user and mobile device.

As discussed above, the steps of FIGS. 11 and 12 may be performed by asession analyzer server 620 or other central computing system, based oncontext data and user input data received from mobile device 610.However, in certain embodiments, some or all of the steps of FIGS. 11and 12 may be performed by individual mobile devices 610 instead of, orin addition to, session analyzer 620. For example, a mobile device 610 amay determine performance conditions individually and/or may receivetransmissions of additional performance conditions for the user from thesession analyzer 620 and/or other mobile devices 610. Using theselocally stored performance conditions, the mobile device 610 a maycontinuously detect and evaluate the current context data of the mobiledevice 610 a, and may generate user notifications and/or contentsuggestions using similar techniques to those discussed above.

Referring now to FIG. 15, another flow diagram is shown illustrating aprocess of determining one or more performance conditions associatedwith a user, based on a user's content resource execution sessions. Theprocess shown in FIG. 15 may be similar to the process described abovein FIG. 9 in several respects. For example, data from the user's contentresource execution sessions, including session context data and sessionperformance data, may be analyzed to determine performance conditionsfor the user. Similarly, the steps in this process may be performed byone or more components in the mobile device session analyzer systems 600described above, such as a session analyzer server 620 and/or mobiledevice 610. However, the steps of FIG. 15, discussed below, describegroups of related execution sessions performed by a user, rather thanindividual execution sessions. For example, a user's overall performancefor a group of content resource execution sessions may be analyzed basedon session group characteristics instead of (or in addition to) thecontext data of individual execution sessions.

In step 1501, data relating to one or more content resource executionsessions may be received, for example, by a mobile device sessionanalyzer 620 from one or more mobile devices 610. Step 1501 or may besimilar or identical to step 901 discussed above. For example, the datareceived in step 1501 may include session data (e.g., user identifier,resource identifiers, execution session start time, execution sessionstop time, etc.), as well as various types of context data, userinteraction data received by the mobile device 610, and any other datacollected in connection with an execution of content resources on themobile device 610. As shown in FIG. 15, step 1501 may execute multipletimes, and thus data for multiple different execution sessions may bereceived, before steps 1502-1506 are performed to analyze and determineperformance conditions based on the execution session data.

In step 1502, after receiving data describing multiple content resourceexecution sessions performed by a user on one or more mobile devices610, the received data may be sorted and grouped into related executionsessions for analysis purposes. For example, the received executionsession data may be sorted to group execution sessions performed by theuser within the same CDN 100 (or 600), such as a specific mediadistribution CDN, a gaming CDN, a professional training or eLearningCDN, and the like. Additionally, within a specific CDN 100 or 600, theexecution session data may be sorted and/or grouped by resource contenttype. For instance, within a gaming CDN 600, the received executionsession data may be grouped into sessions by the specific game and/orgame levels played. For a professional training or eLearning CDN 600,the received execution session data may be grouped into sessions by thespecific training/learning modules, subjects, courses, etc.

In step 1503, one or more performance measurements may be determined forthe user, for each group of content resource execution sessionsdetermined in step 1502. Thus, step 1503 may include similar oridentical techniques to those discussed above in step 902. However,rather than determining performance measurements for individualexecution sessions by a user, the performance determination in step 1503may apply to the groups of execution sessions determined in step 1502.In some cases, performance measurements for session groups maycorrespond to a user scores or evaluations. For example, gaming softwaremay calculate overall user scores for games or game levels completedover multiple execution session by the user. Similarly, professionaltraining or eLearning software may calculate overall user scores basedon automated online tests or other evaluations completed at the end ofan training/eLearning module, course, semester, curriculum, etc.

Additionally, performance measurements of session groups may be based onexpress feedback from the user regarding the group of content resources,such as user content ratings, discussion posts, content evaluations, andthe like, for groups of execution sessions (e.g., training/eLearningcourses, games, television programs, etc.). As discussed above, suchexpress user feedback also may include factors such as the amount oftime the user played/executed the content resources within the group,the user decisions and other interactions during the execution sessionsfor the group of resources, and audio and/or visual cues collected andstored by the mobile device 610 during the group of execution sessions.In some embodiments, the performance measurements determined in step1503 also may include overall consumption velocities and/or remediationrates for the user for the group of execution sessions, rather than forindividual execution sessions as discussed above in step 902.

In step 1504, one or more session group characteristics may bedetermined for each group of content resource execution sessionsdetermined in step 1502. Such session group characteristics may includecharacteristics that apply to groups of execution sessions, rather thanto individual execution sessions. For example, session analyzer server620 and/or mobile devices 610 may determine the number of contentresource execution sessions in the group, the average length of time ofeach content resource execution session, and the average amount of timebetween the content resource execution sessions in the group.

Referring briefly to FIG. 16, an example data table 1600 is showncontaining illustrative session group data. In this example, a number ofdifferent session groups have been defined in the first two columns oftable 1600, each session group correspond to a specific user andspecific CDN/resource type. For each session group, table 1600 includesthe number of execution sessions performed by the user within thesession group, the average length of each session in the group, and theaverage amount of time between each session in the group. It should beunderstood that the session group characteristics used in this exampleare illustrative only and non-limiting. For instance, instead of (or inaddition to) average session length and average time between sessions,additional session group characteristics may include the standarddeviations and variances of the session length and time betweensessions, as well as other statistical measurements determined for eachgroup of execution sessions. Additionally, for each session group inexample table 1600, a performance measure is shown for session group.These performance measurements may correspond to the one or more of thegroup performance measurements determined in step 1503.

In step 1505, the session analyzer server 620 and/or mobile devices 610may determine (or update) sets of user performance conditions for one ormore groups of content resource execution sessions. Thus, step 1505 mayinclude similar or identical techniques to those discussed above in step904. However, rather than determining correlations between context dataand user performance in individual execution sessions, step 1505 mayinclude determining statistical correlations between session groupcharacteristics (step 1504) and the user's performance data for theoverall session group (step 1503). For example, a performance conditionfor a session group may correlate a particular pattern between thenumber, length, and frequency of execution sessions, and a higher orlower level of performance by the user for the session group as a whole.For instance, session analyzer 620 or mobile device 610 may determinethat a user scores consistently better on training/eLearning moduletests when the user studies in short frequent study sessions, ascompared to longer and less frequent study sessions. As another example,the session analyzer 620 or mobile device 610 may determine that a userhas a consistently lower remediation rate when the user reviewstraining/course materials at a frequency of 2 to 7 days, and asignificantly higher remediation rate when the user reviewstraining/course materials at a frequency of greater than 7 days.

In some embodiments, the performance conditions for session groupsdetermined in step 1505 may be similar to those determined forindividual execution sessions, discussed above in step 904. For example,a session analyzer 620 or mobile device 610 may determine pairs ofsession group characteristics (or combinations of session groupcharacteristics), along with corresponding predicted performance effectfor the user (e.g., a Performance+/−on a session group performance pointscale). As with performance conditions for individual executionsessions, certain session group performance conditions determined instep 1505 may apply to individual users, while other performanceconditions may be applicable to groups of users. Additionally, certainsession group performance conditions may be applicable to specific CDNs600 and/or specific types of resources within CDNs 600, while others mayapply to one or more users across multiple different CDNs and/orresource types.

In order to determine the session group performance conditions in step1505, the session analyzer 620 or mobile device 610 may executestatistical analysis techniques to identify a session groupcharacteristic (or combination of characteristics), isolate thecharacteristic(s), and calculate the performance effect of thecharacteristics. For example, the session analyzer 620 may useregression analyses to control for the performance effects of othersession context variables and other session group characteristics,thereby isolating a single session group characteristic (or combinationof characteristics), while effectively holding constant all othervariables affecting user performance during the session group. Afterremoving the potential performance effects caused by other session groupcharacteristic, and individual session context variables, via regressionanalysis, the effect caused by one isolated group characteristic(s) maybe calculated to determine the performance+/−of those characteristics.Similar regressions may be used to isolate analyze the performanceeffect caused by all session group characteristics. Such calculationsalso may take into account (e.g., control for) the difficulty of thecontent resources executed during the session group, based onperformance data from other users executing the same resource groupand/or the performance of the user executing other similar resourcegroups.

In step 1506, session group performance conditions determined in step1505 may be transmitted to one or more user devices. Step 1506 may besimilar or identical to step 905 discussed above. For example, reportsof session group performance conditions may be generated and transmittedto client devices, as well as instructor/administrator devicesassociated with the users. Additionally, as discussed above in referenceto FIGS. 11-14, after a set of session group performance conditions havebeen determined for a user, the current context of the user and theuser's devices 610 may be monitored in order to provide notificationsand suggestions to the user for executing certain content resources atcertain times based on the session group performance data.

For example, referring briefly to FIG. 17, an example of a userinterface screen 1701 is shown on a mobile device 1700. In this example,a notification and content suggestion 1711 is provided to the user basedon an analysis of the user's session group performance conditions withrespect to an eLearning course module. Specifically, in this example, asession analyzer 620 and/or mobile device 610 has determined a suggestedpattern of study session times, frequencies, and lengths for a user,based on the user's session group performance conditions.

A number of variations and modifications of the disclosed embodimentscan also be used. Specific details are given in the above description toprovide a thorough understanding of the embodiments. However, it isunderstood that the embodiments may be practiced without these specificdetails. For example, well-known circuits, processes, algorithms,structures, and techniques may be shown without unnecessary detail inorder to avoid obscuring the embodiments.

Implementation of the techniques, blocks, steps and means describedabove may be done in various ways. For example, these techniques,blocks, steps and means may be implemented in hardware, software, or acombination thereof. For a hardware implementation, the processing unitsmay be implemented within one or more application specific integratedcircuits (ASICs), digital signal processors (DSPs), digital signalprocessing devices (DSPDs), programmable logic devices (PLDs), fieldprogrammable gate arrays (FPGAs), processors, controllers,micro-controllers, microprocessors, other electronic units designed toperform the functions described above, and/or a combination thereof.

Also, it is noted that the embodiments may be described as a processwhich is depicted as a flowchart, a flow diagram, a swim diagram, a dataflow diagram, a structure diagram, or a block diagram. Although adepiction may describe the operations as a sequential process, many ofthe operations can be performed in parallel or concurrently. Inaddition, the order of the operations may be re-arranged. A process isterminated when its operations are completed, but could have additionalsteps not included in the figure. A process may correspond to a method,a function, a procedure, a subroutine, a subprogram, etc. When a processcorresponds to a function, its termination corresponds to a return ofthe function to the calling function or the main function.

Furthermore, embodiments may be implemented by hardware, software,scripting languages, firmware, middleware, microcode, hardwaredescription languages, and/or any combination thereof. When implementedin software, firmware, middleware, scripting language, and/or microcode,the program code or code segments to perform the necessary tasks may bestored in a machine readable medium such as a storage medium. A codesegment or machine-executable instruction may represent a procedure, afunction, a subprogram, a program, a routine, a subroutine, a module, asoftware package, a script, a class, or any combination of instructions,data structures, and/or program statements. A code segment may becoupled to another code segment or a hardware circuit by passing and/orreceiving information, data, arguments, parameters, and/or memorycontents. Information, arguments, parameters, data, etc. may be passed,forwarded, or transmitted via any suitable means including memorysharing, message passing, token passing, network transmission, etc.

For a firmware and/or software implementation, the methodologies may beimplemented with modules (e.g., procedures, functions, and so on) thatperform the functions described herein. Any machine-readable mediumtangibly embodying instructions may be used in implementing themethodologies described herein. For example, software codes may bestored in a memory. Memory may be implemented within the processor orexternal to the processor. As used herein the term “memory” refers toany type of long term, short term, volatile, nonvolatile, or otherstorage medium and is not to be limited to any particular type of memoryor number of memories, or type of media upon which memory is stored.

Moreover, as disclosed herein, the term “storage medium” may representone or more memories for storing data, including read only memory (ROM),random access memory (RAM), magnetic RAM, core memory, magnetic diskstorage mediums, optical storage mediums, flash memory devices and/orother machine readable mediums for storing information. The term“machine-readable medium” includes, but is not limited to portable orfixed storage devices, optical storage devices, and/or various otherstorage mediums capable of storing that contain or carry instruction(s)and/or data.

While the principles of the disclosure have been described above inconnection with specific apparatuses and methods, it is to be clearlyunderstood that this description is made only by way of example and notas limitation on the scope of the disclosure.

What is claimed is:
 1. A method comprising: receiving, by a sessionanalyzer server, session context data from one or more mobile clientdevices associated with a first user, the session context datacorresponding to one or more content resource execution sessions of thefirst user, wherein the received session context data includes devicemovement data detected by movement detection sensors of the one or moremobile client devices; determining, by the session analyzer server, oneor more performance measurements associated with the content resourceexecution sessions of the first user; determining, by the sessionanalyzer server, one or more correlations between particular sessioncontext data and the performance measurements associated with thecontent resource execution sessions of the first user, the correlationsincluding at least one correlation between a particular pattern ofdevice movement and a particular relative performance level of the firstuser; receiving, by the session analyzer server, additional sessioncontext data from the one or more mobile client devices associated withthe first user, the additional session context data including devicemovement data from at least one of the mobile client devices;determining, by the session analyzer server, that the device movementdata received with the additional session context data corresponds tothe particular pattern of device movement correlated with the particularrelative performance level of the first user; and in response to thedetermination, transmitting a notification from the session analyzerserver to one or more of the mobile client devices associated with thefirst user.
 2. The method of claim 1, wherein the device movement datadetected by movement detection sensors of the one or more mobile clientdevices includes: acceleration data detected by one or moreaccelerometers within the one or more mobile client devices; andlocation data detected by one or more Global Position Satellite (GPS)receivers within the one or more mobile client devices.
 3. The method ofclaim 1, wherein determining the performance measurements associatedwith the content resource execution sessions of the first usercomprises: analyzing user feedback data received via an I/O subsystem ofa mobile client device in response to the content resources executedduring the content resource execution sessions.
 4. The method of claim1, wherein determining the performance measurements associated with thecontent resource execution sessions of the first user comprises:calculating a rate at which the first user returns to previouslyexecuted content during the content resource execution sessions.
 5. Themethod of claim 1, wherein determining the performance measurementsassociated with the content resource execution sessions of the firstuser comprises: comparing a set of user inputs received via an I/Osubsystem of a mobile client device during the one or more contentresource execution sessions, to a predetermined set of correct userinputs; and based on the comparison, calculating one or more scores forthe first user for the one or more content resource execution sessions.6. The method of claim 1, wherein the correlations between particularsession context data and the performance measurements associated withthe content resource execution sessions of the first user include: adetermined correlation between a first particular pattern of devicemovement corresponding to a walking behavior of the first user, and acorresponding first relative performance level of the first user withinthe content resource execution sessions; a determined correlationbetween a second particular pattern of device movement corresponding toa jogging or running behavior of the first user, and a correspondingsecond relative performance level of the first user within the contentresource execution sessions; and a determined correlation between athird particular pattern of device movement corresponding to automobiletravel by the first user, and a corresponding third relative performancelevel of the first user within the content resource execution sessions.7. The method of claim 1, wherein receiving the additional sessioncontext data from the one or more mobile client devices associated withthe first user comprises: receiving, by the session analyzer server,periodic transmissions of session context data from each of the one ormore mobile client devices associated with the first user.
 8. The methodof claim 7, wherein the periodic transmissions of session context datareceived from each particular mobile client device includes dataidentifying a current user of the particular mobile client device, and acurrent network of the particular mobile client device.
 9. The method ofclaim 1, further comprising: determining, by the session analyzerserver, a set of performance conditions for the first user, based on thedetermined correlations between particular session context data and theperformance measurements associated with the content resource executionsessions of the first user; and transmitting, by the session analyzerserver, a subset of performance conditions to the one or more mobileclient devices associated with the first user, wherein each performancecondition transmitted to the one or more mobile client devices includesa session context variable and a corresponding value or range of valuesfor the session context variable.
 10. A mobile device session analyzersystem comprising: a processing unit comprising one or more processors;and memory coupled with and readable by the processing unit and storingtherein a set of instructions which, when executed by the processingunit, causes the mobile device session analyzer system to: receivesession context data from one or more mobile client devices associatedwith a first user, the session context data corresponding to one or morecontent resource execution sessions of the first user, wherein thereceived session context data includes device movement data detected bymovement detection sensors of the one or more mobile client devices;determine one or more performance measurements associated with thecontent resource execution sessions of the first user; determine one ormore correlations between particular session context data and theperformance measurements associated with the content resource executionsessions of the first user, the correlations including at least onecorrelation between a particular pattern of device movement and aparticular relative performance level of the first user; receiveadditional session context data from the one or more mobile clientdevices associated with the first user, the additional session contextdata including device movement data from at least one of the mobileclient devices; determine that the device movement data received withthe additional session context data corresponds to the particularpattern of device movement correlated with the particular relativeperformance level of the first user; and in response to thedetermination, transmit a notification to one or more of the mobileclient devices associated with the first user.
 11. The mobile devicesession analyzer system of claim 10, wherein the device movement datadetected by movement detection sensors of the one or more mobile clientdevices includes: acceleration data detected by one or moreaccelerometers within the one or more mobile client devices; andlocation data detected by one or more Global Position Satellite (GPS)receivers within the one or more mobile client devices.
 12. The mobiledevice session analyzer system of claim 10, wherein the correlationsbetween particular session context data and the performance measurementsassociated with the content resource execution sessions of the firstuser include: a determined correlation between a first particularpattern of device movement corresponding to a walking behavior of thefirst user, and a corresponding first relative performance level of thefirst user within the content resource execution sessions; a determinedcorrelation between a second particular pattern of device movementcorresponding to a jogging or running behavior of the first user, and acorresponding second relative performance level of the first user withinthe content resource execution sessions; and a determined correlationbetween a third particular pattern of device movement corresponding toautomobile travel by the first user, and a corresponding third relativeperformance level of the first user within the content resourceexecution sessions.
 13. The mobile device session analyzer system ofclaim 10, wherein receiving the additional session context data from theone or more mobile client devices associated with the first usercomprises: receiving periodic transmissions of session context data fromeach of the one or more mobile client devices associated with the firstuser.
 14. The mobile device session analyzer system of claim 13, whereinthe periodic transmissions of session context data received from eachparticular mobile client device includes data identifying a current userof the particular mobile client device, and a current network of theparticular mobile client device.
 15. The mobile device session analyzersystem of claim 10, the memory storing therein a further set ofinstructions which, when executed by the processing unit, causes themobile device session analyzer system to: determine a set of performanceconditions for the first user, based on the determined correlationsbetween particular session context data and the performance measurementsassociated with the content resource execution sessions of the firstuser; and transmit a subset of performance conditions to the one or moremobile client devices associated with the first user, wherein eachperformance condition transmitted to the one or more mobile clientdevices includes a session context variable and a corresponding value orrange of values for the session context variable.
 16. A computer-programproduct tangibly embodied in a non-transitory machine-readable storagemedium, including instructions configured to cause one or more dataprocessors to perform actions including: receiving session context datafrom one or more mobile client devices associated with a first user, thesession context data corresponding to one or more content resourceexecution sessions of the first user, wherein the received sessioncontext data includes device movement data detected by movementdetection sensors of the one or more mobile client devices; determiningone or more performance measurements associated with the contentresource execution sessions of the first user; determining one or morecorrelations between particular session context data and the performancemeasurements associated with the content resource execution sessions ofthe first user, the correlations including at least one correlationbetween a particular pattern of device movement and a particularrelative performance level of the first user; receiving additionalsession context data from the one or more mobile client devicesassociated with the first user, the additional session context dataincluding device movement data from at least one of the mobile clientdevices; determining that the device movement data received with theadditional session context data corresponds to the particular pattern ofdevice movement correlated with the particular relative performancelevel of the first user; and in response to the determination,transmitting a notification to one or more of the mobile client devicesassociated with the first user.
 17. The computer-program product ofclaim 16, wherein the device movement data detected by movementdetection sensors of the one or more mobile client devices includes:acceleration data detected by one or more accelerometers within the oneor more mobile client devices; and location data detected by one or moreGlobal Position Satellite (GPS) receivers within the one or more mobileclient devices.
 18. The computer-program product of claim 16, whereinthe correlations between particular session context data and theperformance measurements associated with the content resource executionsessions of the first user include: a determined correlation between afirst particular pattern of device movement corresponding to a walkingbehavior of the first user, and a corresponding first relativeperformance level of the first user within the content resourceexecution sessions; a determined correlation between a second particularpattern of device movement corresponding to a jogging or runningbehavior of the first user, and a corresponding second relativeperformance level of the first user within the content resourceexecution sessions; and a determined correlation between a thirdparticular pattern of device movement corresponding to automobile travelby the first user, and a corresponding third relative performance levelof the first user within the content resource execution sessions. 19.The computer-program product of claim 16, wherein receiving theadditional session context data from the one or more mobile clientdevices associated with the first user comprises: receiving periodictransmissions of session context data from each of the one or moremobile client devices associated with the first user.
 20. Thecomputer-program product of claim 16, the including further instructionsconfigured to cause the one or more data processors to perform actionsincluding: determining a set of performance conditions for the firstuser, based on the determined correlations between particular sessioncontext data and the performance measurements associated with thecontent resource execution sessions of the first user; and transmittinga subset of performance conditions to the one or more mobile clientdevices associated with the first user, wherein each performancecondition transmitted to the one or more mobile client devices includesa session context variable and a corresponding value or range of valuesfor the session context variable.